Docker starts containers with restart policy on-failure after host reset

[sammy007]

Description

It's a host failure, not a container failure so none policy should apply in such case. There is literally no way to make docker to act as supervisor for a container which only restarts it in case of container failure.

Reproduce

1. create docker container with on-failure policy
2. restart docker
3. docker ps => 0 containers

a. create docker container with on-failure policy
b. reset HOST
c. docker ps => 1 container

Expected behavior

Do not start container with restart policy set to on-failure after host reset.

docker version

Client: Docker Engine - Community
 Version:           26.1.3
 API version:       1.45
 Go version:        go1.21.10
 Git commit:        b72abbb
 Built:             Thu May 16 08:33:42 2024
 OS/Arch:           linux/amd64
 Context:           default

docker info

Client: Docker Engine - Community
 Version:    26.1.3
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.0
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.27.0
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Additional Info

No response

[mschfh]

I noticed the same issue (with GitHub Codespaces).

The container is started when the Codespace is launched and the docker daemon is started, even if on-failure or unless-stopped is used as restart policy, according to the documentation this shouldn't happen:

on-failure: [...] It doesn't restart the container if the daemon restarts.
unless-stopped: Similar to always, except that when the container is stopped (manually or otherwise), it isn't restarted even after Docker daemon restarts.